Skip to content

chore: version packages - #369

Merged
Bccorb merged 1 commit into
mainfrom
changeset-release/main
Nov 11, 2026
Merged

Bccorb merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

seamless-cli@0.30.1

Patch Changes

  • 3525c5d: seamless init warns when another program already holds a port the local stack publishes (5173, 3000, 5312, 5432, and 5174 with a separate console), and seamless check fails on one. The stack publishes on 127.0.0.1 only, so a Vite dev server on [::1]:5173 used to take http://localhost:5173 in the browser while every check passed. Each warning says what the conflict breaks and how to find the program. check also asks the project's own compose file which services run, rather than matching container names across every running container.
  • 3525c5d: seamless init names each local stack's Compose project after its directory plus a random suffix, and no longer pins container names. A second project scaffolded under a name used before (such as the quickstart's my-app) used to share the first one's Compose project, so docker compose up ran the old project's built images, which crashed against the new starters (does not provide an export named 'requirePermission'), and reused its database. Two scaffolded projects can now also run side by side. Existing projects keep their compose file.
  • 18619ea: seamless verify run without a seamless-auth-api checkout now says it is a contributor tool, where to clone the API, and that seamless check is the command for a scaffolded project. From an npx or global install it no longer prints a path inside the npm cache, and seamless verify --help says the same up front.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from ed4b3cf to fcd4a69 Compare November 11, 2026 13:44
@Bccorb
Bccorb merged commit 68d3300 into main Nov 11, 2026
4 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant